-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update setup script for logs and events #38
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes lgtm. When I search for metric-endpoints
in the repo there are some references in the README. do we plan to update that in a separate PR?
Thanks for the catch, let me make the relevant README changes in this PR |
deploy/README.md
Outdated
``` | ||
|
||
__NOTE__ This script will be executed in bash and requires [jq command-line JSON parser](https://stedolan.github.io/jq/download/) to be installed. | ||
|
||
#### Parameters | ||
|
||
* __-c collector-name__ - optional. Name of Sumo collector that will be created. If not specified, it will be named as `kubernetes-<timestamp>` | ||
* __-k cluster-name__ - optional. Name of the Kubernetes cluster that will be attached to logs as metadata. If not specified, it will be named as `kubernetes-<timestamp>` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so this change only apply to log? (how about metrics/event?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cluster name
attaches the fields:{cluster:CLUSTER_NAME}
to the metadata of the collector, which gets attached to all the logs sent to that collector. Actually since we receive events as logs in Sumo, this should also apply for events. For metrics, you have to set the same CLUSTER_NAME
in the prometheus operator overrides.yaml
prometheus:
prometheusSpec:
externalLabels:
# Set this to a value to distinguish between different k8s clusters
cluster: kubernetes
Eventually this value can be enforced the same in the helm chart when we release that.
* add ad syncing tool * remove test files * go fmt * update env options
-metrics
suffix to metrics sourcessumologic
and include all endpoints in this single secretcluster
field to the collector upon creation to keep it consistent with metricsFYI - @ggarg2906sumo @yuting-liu @lei-sumo